Contact Us on 0800 123 4567 or info@example.com

Mariage

le mariage sous l'ancien régime
March 5, 2007

MIME type testing

Posted by on 05 Mar 2007 in Activity log

We're in a dilemma as to whether to server XHTML documents as application/xhtml+xml, which is correct, or text/html, which is wrong, but more widely supported. This morning I did some testing on various browsers to see what woks and what doesn't:

MIME type application/xhtml+xml

BrowserIMT pagesText pagesSearch
Firefox 2OKNo BG imageOK
Opera 9OKNote link bounces to bottom (target: pseudo-class not supported)Fails (nothing shows up, no errors)
SafariPopups work, but no annotation menuLinks don't workLinks don't work

MIME type text/html

BrowserIMT pagesText pagesSearch
Firefox 2OKOKOK
Opera 9OKNote link bounces to bottom (target: pseudo-class not supported)Fails (nothing shows up, no errors)
SafariOKOKLinks don't work

The results suggest that we really have no choice about using text/html, and even there, we have some problems with AJAX in Safari and Opera which need to be addressed.

March 2, 2007

New alternate CSS for site

Posted by on 02 Mar 2007 in Academic

Spent most of the day monkeying with a new style. It is by no means finished, but you can see it if you manually switch to the Alternate stylesheet.
Bugs(?):
* Opera is very sluggish with this stylesheet
* Firefox displays an odd white band across the top and bottom.

To do:
Fix bugs above
Get the generated code for the side panels adjusted to use my twiddled versions (vert_banner_5.png and vert_banner_6.png) or use all CSS for inserting and placing them.
Decide on menu placement.
Edit table styles
Do we want to twiddle the XHTML display for images? It currently does not include a link for alt.css - and there appear to be other (IMT generated) stylesheets associated with these images - check with Martin.

Thumbnails and links to annotations now working

Posted by on 02 Mar 2007 in Activity log

Finally got the thumbnails working: had to use negative margins on the enclosing div, rather than on the image itself. Tweaked the code a little more to get rid of duplicate returns, and then added functionality so that when you click on a hit which is inside an annotation area, you go directly to the image, with that annotation popping up for you.

Then I worked on getting the category selection list going. It was a bit complicated because the distinct-values we want to test on are attribute values, but the rendered option text we need for the drop-down is the content of a child element. In the end I got it working, so the select element is there on the search page, but at the moment it does nothing. It needs to be hooked up to a block of code which will restrict the text search based on the category, or, if there's no search text, will restrict the document list to those which have annotations in that category.

March 1, 2007

March 1st translation

Posted by on 01 Mar 2007 in Academic

3. Textes tirés d’une source de documents plus grands

Quelques textes de la banque de données sont sélectionnés à partir d’un anthologie plus grande. Ceux-ci ont généralement la structure suivante :



<TEI>

<teiHeader></teiHeader>

<text>

<body>

<div>

<head>[Document title</head>


[Main body of the text]

</div>

</body>

</text>

</TEI>

Dans les cas ci-dessus, l’encodage du contenu principal ("[Main body of the text]") suit les conventions ... ci-dessous dans "Block and inline content markup".

Le teiHeader


L’élément <teiHeader> est mieux documenté par l’utilisation d’un exemple commenté accessible ici. : sample_header.xml.

Encodage d’un contenu pour arrêter et déterminer les lignes.
Block and inline content markup

Les étiquettes suivantes sont utilisées couramment dans ce projet :

*

: Le texte principal est ceinturé dans (entouré par) un
, et d’autres
s peuvent être nichés / (installés) à l’intérieur de celui-ci / (sous celui-ci). Les éléments

peuvent avoir un « type attribute » / les désignant comme “chapitre” ou quelques / toutes autres divisions structurales.

* <head>: Pour les petits texts extraits / pris / à partir de plus grands documents (type 3 au dessus), le titre du texte sera balisé avec une étiquette <head>. Pour les documents plus long et isolés, l’étiquette <head> est utilisée comme des entêtes internes. L’attribut type peut être utilsé pour distinguer le type ="main" du type="sub".

* <p>: étiquette de paragraphe normal.
* <lg> et <l>: les groupes de lignes sont par défaut (be default) des strophes, et des éléments de lignes apparaissent à l’intérieur de celles-ci.

Pour des structures poétiques plus complexes (comme des sonnets), les étiquettes <lg> peuvent être insérées de façon à montrer un groupe de lignes faisant partie d’un plus grand groupe de lignes. Les étiquettes <l> peuvent apparaître seulement à l’intérieur des étiquettes <lg>. Les étiquettes <l> peuvent aussi porter un n attribut indiquant le numéro de la ligne; ceci devrait normalement être fait seulement dans les situations /cas où le texte complet du poème n’est pas inclu (en d’autres mots, seulement où quelques extraits sont balisés), pour indiquer où les lignes sont manquantes.

February 22, 2007

COMPLETED TASK: Enhancement to search

Posted by on 22 Feb 2007 in Activity log, Tasks

It would be useful to add a new drop-down list to the search screen enabling the user to choose to search only within specific annotation categories. (Obviously this search would be limited to images). One great advantage of this would be that we could retrieve sets of annotations, and it would be possible also to pull back thumbnails of the images themselves, so you could look at (for instance) all chickens appearing in the images.

I've spent a little time thinking about this, and there are a few issues to decide before we can plan it properly:

  • Building the select drop-down itself should be straightforward (the same as the other drop-downs).
  • Building the XQuery clause to do this search is not so simple, though; we should shell out to a separate function to do it, as we do with the text search.
  • What we need to pull back is going to be complicated too, especially if it's combined with a text search. It's not exactly clear what the user might intend by searching for "chat" (text) and "Graveur" (annotation category). Does this mean that she's searching for all instances of "chat" that appear in an annotation which is in the Graveur category? Or does it perhaps mean all documents which have annotations in the Graveur category, which also contain "chat"?
  • One approach is to say that if a category is chosen, then the search is restricted to hits within annotations in that category; and what will be retrieved, for each document, is a reduced document which includes only the <rect> and <div> elements for the annotations containing hits; then the XSLT code can process only those annotations, and for each annotation, produce a thumbnail view of the image area using the web-sized version of the image, computing the view rectangle from the original image size and the annotation coordinates.
  • Such an approach could be usefully extended if there were two controls: one checkbox for "Search only in image annotations", which in turn enables the other, "Restrict search to this category of annotation only". If the first checkbox is checked, whatever the search, what is retrieved and displayed would be shown in a thumbnail view.
  • Another option is to say that whenever a hit occurs within an annotation, the XSLT should be intelligent enough to notice that, and render the hit with a thumbnail. This is something we can implement first, and get working, before adding other controls on the page.

On balance, then, we should probably proceed by implementing the thumbnail display in XSLT first, then when that's happy, we should add the filter controls to the search page, and implement the XQuery.

Posting time spent figuring this out...

Fixed title display bug

Posted by on 22 Feb 2007 in Academic

Titles retrieved by the search were displaying twice. This was a stupid XSLT bug; I had this:

$Doc//tei:title[1]

instead of this:

$Doc/descendant::tei:title[1]

Martin and Claire added metadata to IMT files

Posted by on 22 Feb 2007 in Activity log

Newer Image Markup files were lacking metadata and publication statements; older ones had metadata in unstructured <bibl> tags. We trawled through all of them and added proper <bibStruct> tags, with all the information we could gather. There are still lots of gaps, some temporary (where info is available either in notes or from the BN) or permanent (where, for instance, publication date is not known).

Translation markup conventions

Posted by on 22 Feb 2007 in Activity log, Academic

Choix d'encodage
Les documents dans cette base de données sont balisés en format "Text-Encoding Initiative's P5". Voir la page de schémas plus de plus amples détails. Tous les documents utilisent le même schéma, "mariage.xsd" (relié à d'autres filières)

Types de documents
Les documents dans la base de données font parties des catégories suivantes:

1. Images balisées

Les images sont balisées à l'aide de "Image Markup tool" avec le <tei Header>, les conventions normales comme décrites ci-dessous sont appliquées; Le "Image Markup Tool" ajoute toute autre information par lui-même dès que les données sont sauvegardées ou téléchargées, ainsi les informations additionnelles apparaîtront dans le <tei Header> de ces données. À l'intérieur même de ces annotations (lesquelles derrière les scènes sont étiquetées <div>), normal block-elements les éléments normaux "block-level" sont utilisés (<p>, <lg> et ainsi de suite/ etc.), et sous ce niveau des balises les descriptions sont comme suit ci-dessous.

2. Textes autonomes

Les textes autonomes sont des documents tel que des brochures, qui ne font pas partie d’un plus grand texte telle qu’une anthologie. /which do not form part of a larger text/ Ces documents sont normalement balisés en utilisant les structures suivantes :

#

<TEI>

                      <teiHeader></teiHeader>

                      <text>

                         <front>

                            <docTitle>

                               <titlePart type="main">[Document title]</titlePart>

                            </docTitle>

                         <docAuthor>

                               <name>[Document Author]</name>

                         </docAuthor>

                         </front>

                         <body>

                                <div>[Main body of the text]</div>

                             </body>

                         <back>[Optional back matter]</back>

                      </text>

                   </TEI>


#

3. Textes tirés d’une source de documents plus grands

Quelques textes

translation_markup_conventions

Posted by on 22 Feb 2007 in Academic
Choix d'encodage Les documents dans cette base de données sont balisés en format Text-Encoding Initiative's P5. Voir la page de schémas plus de plus amples détails. Tous les documents utilisent le même schéma, mariage.xsd (relié à d'autres filières) Types de documents Les documents dans la base de données font parties des catégories suivantes: 1. Images balisées