XYZ
Coden text
A-999
S0001-9999(00)00100-3
PUBMED Abbreviation
![contact [corresponding='no' postpub='no' biocontact='no' ] contact [corresponding='no' postpub='no' biocontact='no' ]](.//starttag.gif)
Affiliation Title
[email protected]
+99 (0) 123 456 7890
+99 (0) 123 456 7899
www.FirstContact.org


![contact [corresponding='no' postpub='no' biocontact='no' ] contact [corresponding='no' postpub='no' biocontact='no' ]](.//starttag.gif)


Contact Address Line One
Contact Address Line Two
Contact City
Contact State
Zip Code
Contact Country
+99 (0) 123 456 7890
+99 (0) 123 456 7899
[email protected]
www.SecondContact.org
Additional Note on Address




![contact [corresponding='no' postpub='no' biocontact='no' ] contact [corresponding='no' postpub='no' biocontact='no' ]](.//starttag.gif)
Affiliation Title
[email protected]
+99 (0) 123 456 7890
+99 (0) 123 456 7899
www.FirstContact.org


![contact [corresponding='no' postpub='no' biocontact='no' ] contact [corresponding='no' postpub='no' biocontact='no' ]](.//starttag.gif)


Contact Address Line One
Contact Address Line Two
Contact City
Contact State
Zip Code
Contact Country
+99 (0) 123 456 7890
+99 (0) 123 456 7899
[email protected]
www.SecondContact.org
Additional Note on Address




Institution Name
Department


International Address Line
City
Post Code
Country
www.detica.com
First Address Note
Second Address Note



MajorCategoryKeyword
PrimarySubCategoryKeyword
SubCategoryKeyword
SecondSubCategoryKeyword
TopicKeyword
SubTopicKeyword
AnotherSubTopicKeyword

![production-dates [receiveddate='01Jan2004' reviseddate='Mar2004' acceptdate='2004' qaapprovdate='04Apr2004' finalapprovdate='05May2004' webpubdate='06Jun2004' projectedprintpubdate='07Jul2004' printpubdate='07Jul2004' ] production-dates [receiveddate='01Jan2004' reviseddate='Mar2004' acceptdate='2004' qaapprovdate='04Apr2004' finalapprovdate='05May2004' webpubdate='06Jun2004' projectedprintpubdate='07Jul2004' printpubdate='07Jul2004' ]](.//starttag.gif)

This is a comment. Such comments in this test article will be used where it is not feasible to put self-describing text into a structure.
Test articles and test metadata
Self-Describing Software-Stress-Testing Article - Conforming to Article DTD 1.8
version 1.8.0
(Sub Title)

Givenname A. Surname and Secondary Author
![logo [fileref='999999999_logo.jpg' filename='999999999_logo.jpg' ] logo [fileref='999999999_logo.jpg' filename='999999999_logo.jpg' ]](.//starttag.gif)


This article is designed to test the "
Taylor & Francis Journal Article DTD
" (abbreviated to "
TFJA
") and to demonstrate its capabilities. It is self-describing in the sense that the content describes the markup that holds it. For example, a list item might contain the text "This is a list item". This approach helps to detect errors in software that is used to process or present the article content. Software is further "stress-tested" by the deliberate inclusion of complex and unusual combinations of elements and attributes. For example, abstracts often consist of a single paragraph, but this example abstract contains multiple paragraphs and a list (which will confuse or break a program that can only handle a single paragraph).
Note that comments can be added in most locations between text blocks, but not within paragraph text. 
This is a paragraph. Note that paragraphs can contain other block-level objects, such as lists, as well as directly containing text.
Short Section Header
This section demonstrates the use of elements that can occur within blocks (such as titles and paragraphs).
A number of emphasis styles are allowed, including
bold
,
italic
,
small caps
,
underline
,
|box|
,
roman
,
monospaced
and
script
.
It is possible to embed an empasis element within another emphasis element, so any combination of styles can be produced, including
a bold
word
in italic phrase
, and
a
subscript
word in underlined text
, and
an
italic
word in superscript text
, among many other combinations.
An image can be inserted inline, as in ![inlinegraphic [fileref='999999999_photo.gif' height='50' width='25' filename='999999999_photo.gif' ] inlinegraphic [fileref='999999999_photo.gif' height='50' width='25' filename='999999999_photo.gif' ]](.//starttag.gif)
, but other image-related elements should be used for special purposes, such as for figures, logos and article author photographs.
When a new page starts in the initial print publication of an article, the location of the page-break is preserved. This text appears at the end of page 2, and ...
--- [page 3] ---
this text appears at the start of page 3.
A paragraph can be broken into lines using the break elements, in order to include poetry:
[break]
[break]
[break]

Note that there is a block-level element for computer text that is described later, but it is also possible to include computer code, or other lines of monospaced text, using a mixture of the break element and the monospaced emphasis element, as in :
[break]
monospaced line 1
[break]
monospaced line 2

Objects in the text can be isolated and identified using the "name" related elements, including famous names, company names and institution names:
Einstein
,
IBM
and
NASA
. A trademark such as
Java
can be identified. In addition, an acronym such as
BBC
(British Broadcasting Corporation) can be identified, as well as terms, such as
XML
. Names can still be identified within styled ranges of text, such as
italic text with a famous person (
Einstein
) within it
.
Text may include references to various objects within the same article. There is a different element for references to different kinds of object in the article, including:
chemical equation
,
[break]
chemical formulae
,
[break]
chemical structure
,
[break]
citation
,
[break]
end note
,
[break]
figure
,
[break]
supplementary material
,
[break]
footnote
,
[break]
list item
,
[break]
list
,
[break]
math equation
,
[break]
table
,
[break]
enunciation
and
cross (x-ref)
. These links can contain superscript, subscript and emphasis, such as
link-to-W
3
C-
Web
-site
.
Text may also include references to external objects, including
text
, a Web address,
www.detica.com
, and emails
[email protected]
.
This section introduces the elements that construct blocks of text, including paragraphs (such as this one).
Apart from the paragraph elements containing this text, there are also several alternatives, starting with an address:

address line one
[break]
address line two
[break]
City Name
[break]
Country Name
It is not necessary to display an address vertically. Simply leaving out the break-line elements allows for the alternative presentation:

77 Shaftesbury Avenue
,
London
England
tel:
0001 999 1234
or fax:
0001 999 1235
, or email to
[email protected]
and see the Website at
www.detica.com
Blocks of computer text can be isolated. Each line of the computer text is separated from other lines using the br (break) element:
This is my signature (could be a graphic, but if text only
subscript
and
superscript
allowed!


By default, the extract is part of the main narrative flow, but an attribute can be set to make it an independent "side-box", as in the following example:
This extract has a sidebox value of "yes", so it not part of the main narrative flow, and can be floated to any convenient location on a page or screen.

But stanza markup is optional, and redundant when there is a single stanza presented. Either way, the source
of the poem can be added at the end:

Finally, a footnote can be defined:


A text block, such as an extract, can be placed within a paragraph. When placed at the end of a paragraph, there is no real difference to it appearing immediately after the paragraph, but when placed in the middle of a paragraph, it splits the paragraph into two separate text blocks. However, the first text block in the paragraph might be formatted to indicate that a new paragraph has begun (such as by indeting the first line, and putting vertical space above it), while the second will appear directly below the embedded block, as in the text beneath this extract:
so
this
text is not really a separate paragraph, but a continuation of the original paragraph above the extracted text.
The second kind of list is an itemized list, with a prefix that can be pre-defined using the listitemlabel attribute (in this case set to the value "="): 
The third kind of list is an ordered (numbered) list. By default, items are numbered using Arabic numerals:
A numbered list can contain other numbered lists, and rendering software must not become confused and make mistakes in numbering each outer and inner item:
Tables should always now be created as an object (that could be floating).
The "table" element is deprecated, and note that the "tbl" element is the equivalent of
the CALS default "table" element.
The following table has no attributes set, so text should appear vertically in the middle,
and left justified (the frame attribute is set to "sides"). It is a "formal" table, and
has a title:
![table [frame='sides' orient='port' ] table [frame='sides' orient='port' ]](.//starttag.gif)


The following table tests text alignments, both horizontally and vertically (the frame attribute is set to "topbot"):
![table [frame='topbot' orient='port' ] table [frame='topbot' orient='port' ]](.//starttag.gif)
![tgroup [cols='3' ] tgroup [cols='3' ]](.//starttag.gif)
| col: 1 ('col-1') width: 1* |
col: 2 ('col-2') width: 1* |
col: 3 ('col-3') width: 1* |
| Body Rows | ||
|
The cells below this one are aligned horizontally and vertical in all the possible combinations...
|
This column holds a lot of text to help make middle alignments in the first column more obvious.
|
This column is added to help ensure that the second column is narrow enough to force the cell in the first column to occupy at least three lines.
|
|
Middle Left.
|
|
|
|
Top Left.
|
|
|
|
Bottom Left
|
|
|
|
Middle Center
|
|
|
|
Top Center
|
|
|
|
Bottom Center
|
|
|
|
Middle Right
|
|
|
|
Top Right
|
|
|
|
Bottom Right
|
|
|



The following table tests overriding text alignments (entry overrides row, which
overrides tbody), both horizontally and vertically (the frame attribute is set to "top"):
![table [frame='top' orient='port' ] table [frame='top' orient='port' ]](.//starttag.gif)
![tgroup [cols='3' align='right' ] tgroup [cols='3' align='right' ]](.//starttag.gif)
| col: 1 ('col-1') width: 1* |
col: 2 ('col-2') width: 1* |
col: 3 ('col-3') width: 1* |
| Body Rows | ||
|
Right (tgroup element) and Bottom (tbody element).
|
Top (entry element).
|
There is a lot of text here to make sure that
this row spans at least three lines, and therefore shows that the
cell alignments described in the other cells can really be seen to work
as advertised. Quite a lot of text is needed here to ensure that the other cells
will be large enough to show vertical alignments properly. This is the final sentence to
make this cell sufficiently large. Hope this is enough.
|



The following table tests horizontal alignment on a given character ("." and ":"), specified
at the tgroup and colspec levels (also, multiple tgroup elements) (the frame attribute is set to "all"):
![table [frame='all' orient='port' ] table [frame='all' orient='port' ]](.//starttag.gif)
![tgroup [cols='2' align='char' char='.' charoff='50' ] tgroup [cols='2' align='char' char='.' charoff='50' ]](.//starttag.gif)
| col: 1 ('col-1') width: 1* |
col: 2 ('col-2') width: 1* |
| Body Rows | |
|
The cells below this one are aligned on decimal point. (align on ".")
|
The cells below this one are also aligned on decimal point,
because the align attribute is on the tgroup element. (align on ".")
|
|
123.4 (align on ".")
|
5.6789 (align on ".")
|
|
12.34 (align on ".")
|
56.789 (align on ".")
|
|
1.234 (align on ".")
|
5677.89 (align on ".")
|
|
1234 (align on ".")
|
56778.9 (align on ".")
|
|
1234.0 (align on ".")
|
567789 (align on ".")
|

![tgroup [cols='2' ] tgroup [cols='2' ]](.//starttag.gif)
| col: 1 ('col-1') width: 1* |
col: 2 ('col-2') width: 1* |
| Body Rows | |
|
Next cell is character aligned on ":"
|
abcde:f (align on ":")
|
|
Next cell is character aligned on ":"
|
abcd:ef (align on ":")
|
|
Next cell is character aligned on ":"
|
abc:def (align on ":")
|
|
Next cell is character aligned on ":"
|
ab:cdef (align on ":")
|
|
Next cell is character aligned on ":"
|
a:bcdef (align on ":")
|



The following table tests row and column spanning cells, using the morerows attribute
and the namest and nameend attributes (the frame attribute is set to "bottom"):
![table [frame='bottom' orient='port' ] table [frame='bottom' orient='port' ]](.//starttag.gif)
![tgroup [cols='3' ] tgroup [cols='3' ]](.//starttag.gif)
| col: 1 ('col-1') width: 1* |
col: 2 ('col-2') width: 1* |
col: 3 ('col-3') width: 1* |
| Body Rows | ||
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
|
Normal non-spanning cell.
|
Normal non-spanning cell (there is no entry element for the occupied cell before this one).
|
|
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
Normal non-spanning cell.
|
||
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
|
Normal non-spanning cell (and absent entry element before this one).
|
||
|
Normal non-spanning cell (and absent entry elements before this one).
|
||
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|
Normal non-spanning cell.
|



There is a single inline image element, which is used here to refer to the photograph of the author of this article (Einstein himself)...![inlinegraphic [fileref='999999999_photo.gif' height='20' width='20' filename='999999999_photo.gif' ] inlinegraphic [fileref='999999999_photo.gif' height='20' width='20' filename='999999999_photo.gif' ]](.//starttag.gif)
. All of the other images are block-level, including the photograph and logo at the top of this article, but also including:
The final place that an image can be referenced is from within a mathematical structure:
[STRUCTURE]
.
More interesting is the DTD's support for multimedia objects, including video, audio, datasets, and other supplementary material. Supplementary material be tagged as article metadata, or placed in the flow of article text. 
![supplementmaterial [id='suppmat2' contenttype='video' articleid='999999999' productid='productID' doi='10.1234/XXX-123456789-suppmat2' freedownload='yes' attachtoissue='yes' yearofpub='2010' ] supplementmaterial [id='suppmat2' contenttype='video' articleid='999999999' productid='productID' doi='10.1234/XXX-123456789-suppmat2' freedownload='yes' attachtoissue='yes' yearofpub='2010' ]](.//starttag.gif)

First, a single equation, containing just the fomula in text (not the possible TeX markup and graphic versions):
But there is a variant of this element that indicates that it must not break the paragraph apart. This is the "inline" variant: 

inline math formula

. Such formulae will also not be numbered.
Block level equations are usually numbered, but an alternative element can be used to create an unnumbered equation:
But, as with mathematical formulae, a chemical formulae can be officially "inline", using a different element: 
inline chemical formula
. Again, such formula will not be numbered.
Block chemical equations are usually numbered, but a different element is used to create an unnumbered equation:
A structure is represented by an image of the structure, referenced by file name or by entity reference:
[STRUCTURE]
This article was produced in collaboration with several individuals from Taylor & Francis, including Alex Kean, Bob Hech and Ed Cilurso.
Articles supported by funded research may need to identify the sources of the research funding. Funding information in the text of an article can identify the organization that provided funding, and any identification numbers assigned by the organizations. Funding information should be repeated, in greater detail, in the article metadata. This article was funded by
Taylor & Francis
, grants
ABCD
and
1234
.
![ref-periodic [id='loosePeriodic' ] ref-periodic [id='loosePeriodic' ]](.//starttag.gif)
This is a "loose text" periodic publication reference, containing original text and punctuation, but with identified components such as the
Journal Title
and
Article Title
, Volume
2
, Issue
5
, the date (
Jan
2004
), the name of the author (
Neil
A
.
Bradley
Jnr
et al
) and the page number range (
100
-
101
) and DOI
10.1080/9999999999
.

![ref-book [id='looseBook' ] ref-book [id='looseBook' ]](.//starttag.gif)
This is a "loose text" book reference. It has series information (
Book Range
), a
Book Title
and
Chapter Title
, page range (
100
-
101
), author details (
Neil
A
.
Bradley
Jnr
et al
), editor name (
Smith
,
John
Brian
(
Md
)), and publication details (
Abstract Number
for
Publication Name
, published in year
2004
at
London
,
NoState
of
England
).

![ref-conf [id='looseConference' ] ref-conf [id='looseConference' ]](.//starttag.gif)
This is a "loose text" conference reference. It contains details on the conference itself, such as
Meeting Name
, date (
3rd
of
August
,
2004
) and location (
New York
,
New York
in the
USA
), the
Presentation Title
and its author (
Neil
A
.
Bradley
Jnr
et al
) and editor (
Smith
,
John
Brian
(
Md
), and for a publication from the conference its
Collection Work Title
and publication details (
Abstract Number
for
Publication Name
, published in year
2004
at
London
,
NoState
of
England
).

![ref-govpub [id='looseGovPub' ] ref-govpub [id='looseGovPub' ]](.//starttag.gif)
This is a "loose text" government publication refrence. It contains the
Document Publication Title
,
Field
and
Number
, as well as a
Chapter Title
, page range (
100
to
101
), and author details (
Neil
A
.
Bradley
Jnr
et al
), and date 
Feb
4
2010
.

![ref-patent [id='loosePatent' ] ref-patent [id='loosePatent' ]](.//starttag.gif)
This is a "loose text" patent reference. It contains the
Patent Number
and
Patent Title
, the date it was released (
12th July 2001
) and patent owner details (
Neil
A
.
Bradley
Jnr
et al
).

This section demonstrates the ability to divide references into groups. Sections hava a title, and optional leading paragraphs (like this one), but cannot contain embedded sections.
![ref-periodic [id='realPeriodic' ] ref-periodic [id='realPeriodic' ]](.//starttag.gif)


Vermorken
J.B.


Quatalla
J.P.


Hatty
S.R.


et al


Phase I study of gemcitabine using once every two weeks schedule
Br. J. Cancer

1997
76


1489
1493

10.1080/9999999999

![ref-conf [id='realConference' ] ref-conf [id='realConference' ]](.//starttag.gif)


Yamada
M.


On 𝒫-regularity in semigroups and the structure of 𝒫-regular semigroups
Proceedings of the First International Symposium on Algebraic Structure and Number Theory



















Springer

Hong Kong



1998




297
331



French Translation Abbreviation-title