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

Mariage

le mariage sous l'ancien régime
June 18, 2010

Do not leave empty foreign tags

Posted by on 18 Jun 2010 in Academic

I was inserting empty 

<foreign xml:lang="gr"></foreign>

tags as markers for greek text that I couldn't transcribe but that I would go back to once CC had them transcribed by a greek professor. I had trouble figuring out why every time I inserted an empty foreign tag, the text proceeding the tag would display italicized online even though I had rendered the entire paragraph as 

<p rend="font-style: normal;">

Originally, I had tried fixing this problem by putting a 

<hi rend="font-style: normal;"></hi>

tag after every foreign tag, however, MH noticed that this was causing a problem to the XHTML because in some cases the 

<hi>

element was running right over a page break.

MH explained to me that leaving foreign tags without any content in them causes text proceeding the tag to become italicized. As a solution, he suggested that I get rid of all 

<hi rend="font-style: normal;"></hi>

tags following the foreign elements and to instead put a comment tag within the foreign tag: 

<foreign xml:lang="gr"><!-- Phrase grecque à ajouter --></foreign>

As a result, all the text proceeding the tag returned to normal font style.

June 16, 2010

XSLT fix

Posted by on 16 Jun 2010 in Activity log

There's sometimes a need to define a text-align setting to something which can only be enclosed in a <hi> tag, because of the surrounding context (for instance, where you cannot use a head tag because the parent element is a <quote> tag). hi elements give rise to span elements in the XHTML, and these default to display: inline, so I've put in a trap which detects when a text-align setting is applied to a hi tag and adds display: block to the style value. This appears to be working for the examples I know of. At some point there may be more CSS properties that need to act as triggers for this behaviour, and there may also be situations where display: block is not appropriate (such as when an element is floated), so I'll need to watch out for reports of oddities with this.

June 15, 2010

Fixed a bug in XSLT

Posted by on 15 Jun 2010 in Activity log

LSPW reported the Sonnet 1609 was not rendering, due to an ambiguous template match; this turned out to be caused by a link to an external source, whose path mimicked one of our internal paths. I've now made the internal path match much more specific, so the match is much more unlikely. It's still not impossible, though -- I should probably come back to this.

June 9, 2010

Encoding for left-aligned header with indented text

Posted by on 09 Jun 2010 in Academic

I've recently encountered two dedications with headers that looked like the following:

In order to encode the text so that all lines after the first line are aligned to the left and indented by about 1em, it's necessary to use the following encoding:

<div type="dedication">
<fw type="folioNum" place="top-right" rend="float: right;">71</fw>
				<head rend="text-align: left; margin-left: 1em; text-indent: -1em; font-size: 110%;">
				<figure><figDesc>Petite gravure</figDesc></figure>
				<hi rend="font-style: normal; font-size: 150%; letter-spacing: 0.2em;">A NOBLE HOMME</hi><lb/>
				<hi rend="font-style: normal; font-variant: small-caps; font-size: 150%; letter-spacing: 0.2em;">Gvillavme Anefrie</hi>,<lb/>
				<hi rend="font-style: normal; font-size: 110%;">ſieur de Chaulieu , Conſeiller du<lb/>
				Roy en ſa Cour de Parlement à<lb/>
				Rouën , & Commiſſaire aux Re-<lb/>
				queſtes dudit lieu</hi>.<lb/>
				</head>
June 7, 2010
May 27, 2010

Documents to be updated with the new link system

Posted by on 27 May 2010 in Activity log, Tasks

Further to my last email, these are the files that need to be updated because they contain the old <note type="link">.

Image files:

  • agresseure
  • balance
  • bonheur_des_uns
  • chat
  • corrige_si_tu_peux
  • invention_femmes_1
  • invention_femmes_2
  • grande_destruction
  • le_bon_menage
  • martires
  • massacre_lagniet
  • massacre_larmessin
  • operateur_cephalique

Text documents:

  • advis_salutaire
  • purgatoire
  • reconfort_des_femmes
May 26, 2010

Starting to do fixes for old multiple linking system

Posted by on 26 May 2010 in Activity log

Way back at the beginning of the project, we had a system for creating multiple links between documents. That's no longer functioning, because we now have a more sophisticated linking system based on the new db structure. However, the old links still persist in some of the original documents, and they're not working properly. This is what needs to be done:

  • Find all instances of <note type="link">. Typically, these contain a block of text surrounded by a <ref> tag with multiple targets. The text needs to be rebuilt with more logical links made from ref tags around specific mentions of individual targets in the text.
  • Many of the original links pointed to specific locations in the target documents based on ids. These ids were assigned to the ref tags originally, but that really doesn't make much sense in the case of engravings; we should be linking to the target annotation using the formula ann_imtArea_10. Those targets should be updated appropriately. In the case of items in the text documents, it's OK to give a unique id to the <ref> tag, but that will need to be passed through by the XSLT (which I don't think is happening right now).
  • Finally, we need to document this on the blog with step-by-step instructions.

I've started this process with some edits to <il_cherche.xml> and <la_femme_battant.xml>, but haven't finished them yet.

May 25, 2010

Distinguishing original notes from CC's notes

Posted by on 25 May 2010 in Academic

I just figured out a way to distinguish between notes added by CC to original documents and those that appear as part of the original document.

Notes that are part of the original document may be written like this:

hi rend="vertical-align: superscript; font-size: 80%;"

The number of the footnote would go inside that <hi rend> tag. Then, at the bottom of the document, the note, encoded like this:

p rend="font-size: 80%;

... and the note would go inside that <p> tag. For notes added in by CC, we can just use the generic <note> tag.

Margin-top/Margin-bottom

Posted by on 25 May 2010 in Academic

I learned recently that the mark-up I had been doing to get rid of line breaks between line groups in poems wasn't quite right, so I just wanted to post the correct mark-up as a reference point for myself (and others who might make the mistake, too).

Instead of using:

lg type="stanza" rend="margin-top: 0; margin-bottom: 0;"

On the top line group, I would want to use:

lg type="stanza" rend="margin-bottom: 0;"

... and on the bottom line group,

lg type="stanza" rend="margin-top: 0;"

And this mark-up would get rid of the space between these two line groups!

Fix for bug showing up in Candale

Posted by on 25 May 2010 in Activity log

LCC reported a problem with the Candale texts, which showed up recently -- we don't know what actually caused it to appear now, since the relevant part of the text has apparently not changed, but his is the bug profile:

The content of the document has this:

<fw type="sig" place="bot-center" rend="text-align: center; 
           margin-left: auto; margin-right: auto;">I. Part.<space quantity="4" unit="em"/>A</fw>

This is the XSLT which creates the error:

<xsl:variable name="fwContent" select="normalize-space(./text())"/>

The input to normalize-space() becomes a sequence of text nodes, which is not allowed; you get the error "A sequence of more than one item is not allowed as the first argument of normalize-space()". This is a working solution:

<xsl:variable name="fwContent"><xsl:value-of separator=" " select="normalize-space()"/></xsl:variable>