The Communications of the TEX Users Group Volume 29 ... - TUG

More documents

Recommendations

Info

$E-m: Guidelines for Future TEX Extensions - TUG$

$TUG 2001: A TEX Odyssey PROGRAM$

$LATEX Sophisticated professional typesetting for business and ...$

$TEX and Scripting Languages - TUG$

$Geometric Diversions with TEX, METAFONT and METAPOST - TUG$

$Writing Gregg Shorthand with mEtaFoNt and LATEX - TUG$

$Generating LaTeX documents through Matlab - TUG$

Krisztián Pócza, Mihály Biczó and Zoltán Porkoláb In the next sections the structure of OOXML will be briefly discussed; first, let us review the idea of runs. A run is a piece of text which also has some style specification. Runs are placed and removed dynamically while the Word document is edited. A sentence or even a word can be divided into more than one run with the same style. The component called TeXizer is responsible to join runs having the same style to a simple run in the outgoing TEX code and break the source line length at some predefined value (default is 72). The previous description is illustrated by the UML sequence diagram in Figure 1. 4 Features of docx2tex In this section we list the supported and the unsupported features of docx2tex. Figure 1: UML sequence diagram 4.1 Supported features Docx2tex supports the following features of Word 2007 and TEX: 1. Normal text 2. Italic, bold, underlined, stroked, small capitals, . . . 3. Left, right, center aligned text 4. Headings and sections, three levels 5. Verbatim text 6. Style mapping 7. Simple tables 8. Line and page breaks 9. Numbered and bulleted lists 10. Multilevel lists and continuous numbered lists 11. Figure, table and listing captions 12. Cross references to captions and headings 394 TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting
13. Image conversion from various formats (including .png, .jpeg, .emf, etc.) to .eps 14. Substitution of special characters (e.g. \, #, {, }, [, ], %, &, ˜, . ..) 15. Text boxes 16. Basic math formulae, Word Equations support docx2tex supports normal and special text styles and also text alignments. We support heading styles Heading1, Heading2, and Heading3 that convert to \section, \subsection, and \subsubsection respectively. Word does not support verbatim text while TEX does. To work around this deficiency, text marked with Verbatim style is converted to verbatim text surrounded by \begin{verbatim} and \end{verbatim}. There are many cases where we are required to use different styles for headings or even verbatim. Only simple, left-aligned tables are supported. Both numbered and bulleted lists are supported, including mixing and nesting. Continuous lists are also supported using the \setcounter, \enumi, and \theenumi commands. Figure, table and listings captions are recognized and we support referencing them; likewise with heading references. Image references are resolved and the images (mainly .png and.jpeg) embedded in the OOXML documents are converted to .eps. The width and height properties are queried and the same properties are used in the resulting TEX documents. Some special TEX characters are also resolved and escaped in the resulting TEX document. Text found in Text Boxes of Word documents are also processed and inserted in place of the resulting TEX document. 4.2 Unsupported features Docx2tex has only basic Word Equations (mathematical formulae) support at the time of publishing this paper. We plan to add more support for Word 2007 Equations and Drawings that can be converted to TEX mathematical formulas and xfigs respectively. Both of them are described in XML format therefore our standard solution can be extended without introducing other technologies. 5 A complex example In this section we will show a complex example broken into significant parts that introduces the most important features of docx2tex. 5.1 The structure of the OOXML ZIP package To inspect the content of an OOXML ZIP package we first unzip the contents of our Word 2007 document to a directory and get a recursive directory listing: docx2tex: Word 2007 to TEX PS C:\Phd\conf\2008_4_tex\example.docx> ls -Recu |% {$_.FullName.SubString(30)} example.docx\customXml example.docx\docProps example.docx\word example.docx\_rels example.docx\[Content_Types].xml example.docx\customXml\_rels example.docx\customXml\item1.xml example.docx\customXml\itemProps1.xml example.docx\docProps\app.xml example.docx\docProps\core.xml example.docx\word\media example.docx\word\theme example.docx\word\_rels example.docx\word\document.xml example.docx\word\fontTable.xml example.docx\word\numbering.xml example.docx\word\settings.xml example.docx\word\styles.xml example.docx\word\webSettings.xml example.docx\word\media\image1.jpeg example.docx\word\theme\theme1.xml example.docx\word\_rels\document.xml.rels example.docx\_rels\.rels The most important part is the document.xml file that contains the document itself and references to external items. The numbering.xml file specifies the style of the numbered or bulleted lists contained in document.xml. The styles.xml file specifies information about the styles used in the document. Under the media subdirectory the embedded images can be found (image1.jpeg in our example). 5.1.1 Structure of the document The text in the document.xml file is grouped into paragraphs. Every segment of the document is a paragraph (normal text, heading texts, images, etc.) except for some special elements like tables. Paragraphs are further divided into runs. A run is a piece of text that also has some style specification. 5.2 Text conversion The most fundamental feature of tools like docx2tex is the ability to interpret text runs with many basic styling properties and convert them to TEX format. Consider the following example sentence: This is a sentence that contains text with different formatting . This sentence looks like the following in OOXML: TUGboat, Volume 29 (2008), No. 3 — Proceedings of the 2008 Annual Meeting 395
Page 1 and 2: The Communications of the TEX Users
Page 3 and 4: TUG2008 Proceedings University Coll
Page 5 and 6: TUG 2008—program Monday, July 21
Page 7 and 8: At the reception. Around the front
Page 9 and 10: Taco Hoekwater, inside the Beamish
Page 11 and 12: Another, equally large, disadvantag
Page 13 and 14: This “saves” the original \text
Page 15 and 16: Figure 5: Macro result pushed back
Page 17 and 18: TEXworks: Lowering the barrier to e
Page 19 and 20: Direct and reverse synchronization
Page 21 and 22: The TEXnical terms used to describe
Page 23 and 24: 6.2 An orthogonal implementation On
Page 25 and 26: In fact, the text editors and the v
Page 27 and 28: albanian greek norwegian belarusian
Page 29 and 30: input manually, but are generated b
Page 31 and 32: 1.2 Commercially available software
Page 33 and 34: If L ATEX can fit the snippet into
Page 35 and 36: Pascal MetaPost, but using CWEB as
Page 37 and 38: The TEX-Lua mix Hans Hagen Pragma A
Page 39 and 40: \setbox0=\hbox{x}\the\wd0 In Lua we
Page 41 and 42: start.char = uc return true end end
Page 43 and 44: stream-based approach, this time th
Page 45 and 46: example is support for OpenType fon
Page 47: typesetting system is TEX [4] creat
Page 51 and 52: the mapping file example.paraStyleN
Page 53 and 54: The second author accepts or reject
Page 55 and 56: Languages for bibliography styles J
Page 57 and 58: @STRING{srd = {Stephen Reeder Donal
Page 59 and 60: # # standard footnote format (latex
Page 61 and 62: . , \bbled \bbleds .
Page 63 and 64: Languages for bibliography styles (
Page 65 and 66: References [1] James C. Alexander:
Page 67 and 68: Vistas for TEX: liberate the typogr
Page 69 and 70: - even direct formatting instructio
Page 71 and 72: e that quick, simple and clear rend
Page 73 and 74: see that there are slight differenc
Page 75 and 76: Creating cuneiform fonts with MetaT
Page 77 and 78: Definition of encoding (Unicode) Pl
Page 79 and 80: epresentation with proper path dire
Page 81 and 82: When it came to implementing the T1
Page 83 and 84: 4.3 OpenType math in new TEX engine
Page 85 and 86: However, there have always been exc
Page 87 and 88: [2] Nelson Beebe: Character set enc
Page 89 and 90: Meta-designing parameterized Arabic
Page 91 and 92: on the pen direction at each point
Page 93 and 94: % Description for isolated ’alif
Page 95 and 96: Figure 15: Tracing a word from left
Page 97 and 98: Table 1 shows the MOS scores for in
Page 99 and 100:
P3 P3 P3 Q2 Q2 Q2 � � W3 W3 W3
Page 101 and 102:
abridged form, it looks like this:
Page 103 and 104:
with extensions is still somewhat m
Page 105 and 106:
local rx, ry = second.y_coord - ty,
Page 107 and 108:
\startreusableMPgraphic{name}... \s
Page 109 and 110:
the macro \testengine sees two argu
Page 111 and 112:
and exhyph-uk.tex, respectively. Th
Page 113 and 114:
stand for markers of semiconsonants
Page 115 and 116:
y finite state transducers (FSTs).
Page 117 and 118:
local p = hpack(copy(h.list)) lastl
Page 119 and 120:
with PDF documents. Several new tec
Page 121 and 122:
Advanced features for publishing ma
Page 123 and 124:
Page 125 and 126:
— — — — — — — — Fig
Page 127 and 128:
Page 129 and 130:
telegraph. The relatively recent di
Page 131 and 132:
1: [ type: unichar, code: 0073 ] ]
Page 133 and 134:
5 Conclusions The model introduced
Page 135 and 136:
4 Why TEX files and not other marku
Page 137 and 138:
The galley Module or: How I Learned
Page 139:
TUGboat, Volume 29 (2008), No. 3 48
Page 142 and 143:
488 TUGboat, Volume 29 (2008), No.
Page 144 and 145:
TUGBOAT Volume 29 (2008), No. 3 Tab
show all

The Communications of the TEX Users Group Volume 29 ... - TUG

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?