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

Mariage

le mariage sous l'ancien régime
August 11, 2011

More on regularizations

Posted by on 11 Aug 2011 in Activity log

More research on the regularizations suggests that those which handle i/j and u/v variation are also unnecessary in the original transcription field. Using this XQuery, I was able to identify 573 choice elements which have 340 distinct variants:

xquery version "1.0";

declare default element namespace "http://www.tei-c.org/ns/1.0";

let $list :=
(
for $c in //choice[orig]
where translate($c/orig, 'sſuvUVijIJ', '') = translate($c/reg,  'sſuvUVijIJ', '')
return concat($c/orig, '  :  ', $c/reg)
),
$distList := distinct-values($list)
return 
(concat(count($list), ' items, of which there are ', count($distList), ' distinct values: '), 
$distList)

If CC agrees that all these are irrelevant, it would be easy to remove them. That would leave 247 other regularizations, which mainly seem to consist of supplying missing spacing and apostrophes. These could presumably be kept.

Fixes to image markup files

Posted by on 11 Aug 2011 in Academic

I discovered when validating documents that some had information missing from their headers (part of the Image Markup Tool header info, perhaps dating back to a version of the IMT that didn't handle that data properly under Wine on Linux). Fixed those, and also fixed some errors in il_cherche.xml, which had one annotation that was classed as an Objet but actually contained transcription.

Latinate abbreviations in five engravings now marked up

Posted by on 11 Aug 2011 in Activity log

I've completed the markup of all the latinate abbreviations identified by CC in the five engravings which contain them; I've also found what I think is one more instance of apostrophe-with-dot-below used for -(m)ent, which I've marked up without a description, waiting for word from CC.

I tweaked the title attribute so it begins with the expansion, for additional clarification.

Normalizing the use of choice/orig/reg

Posted by on 11 Aug 2011 in Activity log, Tasks

Arising out of a discussion with CC: The intended use of <choice>/<orig>/<reg> in the original transcriptions of the engravings is to restore normal contemporary usage, while the modern transcription is a full modernization. However, there are instances of <choice>/<orig>/<reg> which are used to replace long s with short s (dating back to when we had no modernizations), so these are inconsistent with our policy, and we should get rid of them. I might be able to do this entirely mechanically -- in the case of any regularization where the only difference is between long and short s, I can simply replace the entire <choice> element with the contents of <orig>; while for every regularization where a long s exists in the <orig> but other things are also regularized in the <reg>, I can add an attribute we can use temporarily to find and manually fix them. This is now on my task list.

August 10, 2011

Implemented gaiji markup plan

Posted by on 10 Aug 2011 in Activity log

I've added the required tagging to billet_doux.xml, which has five odd abbreviations of two different types, and implemented the XSLT and CSS to render it as planned. I'm now waiting for textual descriptions in French from CC of the individual symbols, then I'll make the same changes to the other four files which contain the abbreviations.

In the process, I had to modify the schema, which I did using Roma 2, starting from the previous ODD file (mariage_2011_02.odd), and simply adding the gaiji module and a couple of other things. That seemed to work fine, except for the file forest_nuptiale.xml, which was showing validation errors on the @rend attribute when it appears in argument. This was weird, because exactly the same structures validated fine in other files. After some work comparing files, I discovered that the forest_nuptiale.xml file had this declaration:

<?oxygen RNGSchema="../../mariage.rng" type="xml"?>

while other files such as le_bon_mariage.xml had this:

<?oasis-schema href="../../mariage.rng" type="application/xml"?>

Changing to the oasis-schema declaration made the file valid for some reason. Weird, but worth noting in case it crops up again. Other files have combinations of both schema declarations. I should clean up those inconsistencies.

Minor bugfix

Posted by on 10 Aug 2011 in Activity log

When adding XSLT processing for the <head> tag, I had neglected to suppress its processing inside <lg> during both the <lg> scenarios (one of which uses <ul>, while the other uses <div>s and <span>s because <fw> tags appear inside <lg>s). <head> is now rendered first, and suppressed later, in both scenarios.

August 9, 2011

Plan for abbreviations in engravings

Posted by on 09 Aug 2011 in Activity log, Tasks

The abbreviations deriving from Latin, listed in CC's post, will be handled like this:

  • Each distinct abbreviation will have a <glyph> element in the <charDecl> section of the file header, explaining it briefly.
  • Each instance of the abbreviation will be marked up in the original transcription following this pattern: 
    <choice>
  <abbr>Vo<hi rend="vertical-align: super;"><g ref="#theGlyphTag">9</g></hi></abbr>
  <expan>Vous</expan>
</choice>
  • The XSLT will display ONLY the rendered <abbr> element, and will give it a @title attribute for mouseover which is constructed from the information in the <glyph> element(s) referenced inside the <abbr>. This differs from a regular <choice>/<abbr>/<expan>, in which the <expan> is used as the @title attribute. The actual expansion will normally be available to readers in the modernized transcription, since these all occur in the engravings.
August 8, 2011

Bug fixes and enhancements

Posted by on 08 Aug 2011 in Activity log

The following updates and changes were made in response to problems and new feature requests, in consultation with LSPW:

  • A bug was fixed whereby the wrong document title was being used when showing the list of "Liens à cette référence dans les documents". I was using the first trunc title in the monogr, which was wrong when the document was an analytic.
  • A new value ("éloge") for text class has been added, and four documents use it, so we've added a new menu item for these documents to give them their own TOC. In the process, I noticed that the sort-by-type function was not using the TitleSortComparator, so it was sorting éloge after everything else; that's now been remedied.
  • There's a need to allow <head> inside <lg>, so I've added processing for that.
  • Various documents had become duplicated under different names in SVN and in the exist db, so we went through the process of cleaning that up.

Finally, we looked at the possibility of using OCR to handle the Tableau de l'Amour Conjugal. I installed the Tesseract back-end along with a sourceforge front-end called gImageReader, and also the Hunspell and MySpell French dictionaries, and we tried it out, using Simple Scan to get the image, the GIMP to clean it up a bit, and gImageReader to OCR it. The results aren't great, because the quality of the original document is not good, but it might be slightly quicker than straight transcription.

August 7, 2011

Abbreviations in engravings

Posted by on 07 Aug 2011 in Academic

Alphonse Chassant, Dictionnaire des abréviations latines et françaises, explains the transition from Latin abbreviations used in manuscripts (from Antiquity through the Middle Ages) to print culture in the 16th century, and how versions of these Latin abbreviations slipped into French printed texts. The phenomenon of such abbreviation disappeared over the course of the 17th century, but one of its latest manifestations was on engravings, where there was at times little room for the desired text.

There are not really named glyphs for these abbreviations when used in French, but we can say that they follow the tradition used in Latin of contractions and ellipsis, for example; these are two the forms of abbreviation we commonly find in the engravings in our corpus. Building on that Latin tradition, Chassant shows specific examples that cover all of the instances listed below. The page number in his book is given in each case.

(N.B.: Chassant also shows how a horizontal line could replace an "m" or an "n" in Latin abbreviations, the only abbreviation that remained common in print in 17th-century France, usually marked by a tilde. There are six such examples in the "mariage" engravings, but I have not listed them as this abbreviation is not only common throughout the corpus, it also is qualitatively different from the others, replacing a letter rather than indicating a specific word.)

For the following abbreviations, I think the best strategy will be to include a note in the transcriptions, but I'll talk with MH about this before making any moves. (AC = Chassant. Full reference: Alphonse Chassant, Dictionnaire des abréviations latines et françaisesusitées dans les inscriptions lapidaires et métallique, les manuscrits et chartes, 2e édition, Paris, Auguste Aubry, 1862. Google Livres, 6 août 2011.)

0619645 Dame recevant un billet doux "nous" x 4 (AC, p. 132); "qu'il" (AC, p. 136)

72-B-59070 La femme qui fouette son mary "vous" x 11 (AC, p. xxxii--a form of the Latin abbreviation for "us"); "pour" (AC, p. 134); "votre" x 2 (AC, p. 139)

G-153297 Le massacre de Lustucru (Larmessin) "pour" x 2 (AC, p. 134); "vous" x 4 (AC, p. xxxii--a form of the Latin abbreviation for "us" = 9); "votre" (AC, p. 139)

G-157562 Bonheur des uns "que" (AC, p. 136)

P123-IFFNo.190 Opérateur céphalique "pour" (AC, p. 134)

July 26, 2011

Final proofing tasks for Le blanc 07-26-2011

Posted by on 26 Jul 2011 in Academic

Today is my last day, so I am revising my comprehensive list of issues still needing to be worked out on Le blanc and creating an updated one. There is still a lot of editing to be done on this text, and due to its gargantuan size, the edits may take a while. I'm sad to leave it, though, since it's a great read, and I hope that the next person working on it enjoys it as much as I have.

  1. <titlePage>: I had used a “text-indent: 7em” on “& de quelques Sainctes, qui ont beaucoup” but the margin was very off. On 07-19-2011 I used a "text-indent: -1em" in the same place and it made it too far left. At this point, I tried taking out the "text-indent" altogether and made the "padding-left" a -0.5em instead of 0.5em. This also hasn't worked and it is currently 3:33, so I am handing this task over to mholmes, because lspwong and I have spent a good half-hour trying to fix it. :)
  2. There is also a strange space between two lines of the “Avant-propos” (“Dieu vangeur & ennemi” / “des blasphemes...”, as though I had put two or three line breaks between the two lines of text. lspwong checked my code and we're not sure why this strange line break keeps appearing.
  3. Chapter headings and section (of chapter) headings:
    All <head> tags are automatically left-aligning. lspwong looked at this and seems to think my coding is correct, so we're not sure why they aren't centering.
    - i. pgs. 1 to 429: font sizes and font styles (italicized or not) are inconsistent in <head> tags. There is also white space that appears before and after these <head> tags automatically, without me having to put in <lb/> tags. mholmes you'll notice that in instances where the .pdf has no space between a given header and the surrounding paragraphs, I have used a "margin-top: 0; margin-bottom: 0;" to compensate.
    - ii. pgs. 430 to end: font sizes and styles are fine. mholmes you'll notice that I've had to add in <lb/> tags in cases where the .pdf shows white space between the headers and the paragraphs.
  4. Each of the title pages corresponding to the different "livres" (Livre deuxieme, etc.) is also left-aligned, despite being wrapped in a <head> tag as well.
  5. p. 1: the “1.” should be to the left of the drop-cap “I”, as it is in the .pdf, and in the .xml, the drop-cap is to the left of the page number. This also occurs on pgs. 14 and 23.
  6. Please refer to my post from 07-04-2011 for outstanding “Table des chapitres” problems for mholmes to look at.
  7. In the arguments, I have sometimes used a [?] to signal that I was not able to read the text. I was planning on proofing all of my arguments (not just those with the [?]s) by entering the text into sites like Biblos and seeing what I came up with. I will not get a chance to do this before I go.
  8. References need to be done.
  9. Right-aligned arguments (appearing in the right margin of the text) were spaced too far away from the text. I tried changing the number of ems to get them to line up closer with the body, just as the left-aligned arguments do. Most of the adjustments look great now, but the ones on the very first few pages of the "Avant-propos" may still need a bit of tweaking.