== Summary ==
teitohtml and teitodocx render <q> inconsistently
== Versions ==
OS: Ubuntu 12.10
I'm using a checkout of the svn tree:
$ svn update
At revision 11239.
And the installed version:
$ apt-cache policy tei-p5-xsl2
*** 6.18 0
== How to Reproduce ==
1. Download the attached zip file.
2. Unzip. Cd into new directory.
3. Adapt the Makefile to change the values of APPHOME to those appropriate to your system. See the comments in the Makefile.
This will produce test1-fmt.html and test1.docx from test1.xml. The files will be in "shared" subdirectory. These files will be built from whatever TEI version is installed on the system.
$ make SVN=1
This will produce test1-fmt.html and test1.docx from test1.xml. The files will be in the "svn" subdirectory. These files will be built from the svn checkout.
The -fmt.html files are the same as the corresponding .html files, formatted for readibility.
== Actual Results ==
There will be a number of differences between the HTML files produced by the svn checkout and the latest TEI release, I'm only showing the relevant difference below:
$ diff shared/test1-fmt.html svn/test1-fmt.html
< <p>John doe said that <span class="cit">‘hamsters ate all my food!’<span class="bibl"> (John Doe 1992)</span></span></p>
> <p>John doe said that <span class="cit"><span class="q">‘hamsters ate all my food!’</span><div class="biblfree">John Doe 1992</div></span></p>
Visually, the bibliographical information went from being inline and put in parentheses to being a block appearing in italics after the quote.
The two docx files are quite similar to one another (except for an author name appearing in the file generated by the svn version of TEI). However, in these files the <q> element is represented as a block whereas it was inline in the html files.
== Expected Results ==
I'm fairly certain that the vast majority of users would expect the <p> element I've put the XML to appear the same in the various target formats supported by the teitoX tools, as far as it is reasonably possible to do so.
I would expect everything to be inline both in the html and the docx.
== Observations ==
I've always been under the impression that <q> is meant to represent inline quotes. When I look at the examples in the TEI P5 specs, I think I'm right but when I stumbled on the cases above, I started to doubt my understanding.