I frequently use rsync and robocopy to back up my data across multiple systems; it will typically go from my Windows PC at work to the backup (Linux) server, and thence through my Mac laptop at home to my Apple Time Capsule NAS. I've noticed that accented characters in filenames are causing problems for the second stage of this process; files are failing to back up because rsync cannot handle the accented characters in the file names. Since we currently have only two such files in the XML markup, I've decided to avoid the problem rather than solve it, by changing those filenames (and the associated xml:id attributes on their root elements) to ASCII representations. This has no consequences for anything except the file systems, but it keeps everything simple and it'll make backups more reliable.
Worked through JT's proofed copy of one of the vol 17 articles, making changes, until near the end, when it became clear we haven't really made our minds up finally whether we want headline case everywhere, or whether there are places that should have sentence case. Waiting for feedback from JT on that.
JT came by with substantial corrections to vol 17 articles, which I'll try to get done this week. At the same time, we created, uploaded, and linked a PDF of the Notes for Contributors, which was not previously available on the site.
Added some new bio and abstract data to McCreesh, and fixed a bunch of coding errors related to citations and references in Helgason, reported by the author.
I tried to build the PDF of volume 17, including some newly-marked-up documents, for a while without success. I kept getting the error message "The system cannot find the file specified." It turned out that the xep.bat file in the RenderX\XEP folder, which is called by oXygen to transform the FO to PDF, had the path to an old 1.5 JRE which I'd deleted. I replaced it with a working 1.6 JRE path, and everything seemed to work fine. Reported the new volume size (112 pages) to John.
There are quite a lot of obvious problems with the newly-marked-up volume 17 files. We'll have to proof carefully.
After fixing the first bug, the contents page title was not being correctly selected; it defaulted to "Reviews". The logic of the XSLT was correct, but perhaps due to some Cocoon cacheing or some other oddity, it wasn't producing the correct result, so I added an "any" value in the XML, and trapped for that explicitly, working around the issue.
Sorting code in the proofing page was mirrored from the articles and reviews pages, but because it combines both, it didn't quite work correctly; when you clicked on a header to sort the list, it defaulted to showing only articles. This is now fixed.
The first document is marked up, with little difficulty, and I made SM a user on the db so that she can upload documents into it (replacing LN). She proofed the doc against the rendered view on the site, and everything looks OK, but I haven't taken a very close look yet.
Over the last couple of days, ScanCan has got under way again, with a new research assistant (SM, whom we know from the Lansdowne video project), and a new article for volume 17. I set up a test master for volume 17 with the seven docs we have already, and it comes to only 60-odd pages, so one more article won't be enough, but JT says there are more in the pipeline.
Meanwhile, SM is getting up to speed with XML/TEI, and today started her first markup by working on the <teiHeader> and the bibliography of the new article. Everything's going well, although there are (as always) some bibliography items that don't quite fit any of the existing profiles we have from previous documents, so new policy/conventions/rendering code will be needed.
JT pointed out that some documents on the Proofing page were not rendering correctly as PDFs; the process failed with an XSL-FO error. I investigated this, and found that the problem was caused by empty elements for the page numbers:
<biblScope type="start-page"></biblScope> <biblScope type="end-page"></biblScope>
I started by confirming that this was the cause, by commenting them out (they're not needed anyway until the print publication finalizes the page numbers). Then I went back to fix the actual XSLT, and found the problem in the pdf_main_templates.xsl file, in the GetStartPage template. That's now doing some checking on the value of the tag before returning it, going from this:
<xsl:template name="GetStartPage">
<xsl:param name="DefValue"/>
<xsl:attribute name="initial-page-number">
<xsl:choose>
<xsl:when test="//teiHeader/fileDesc/sourceDesc/biblStruct/monogr/imprint/biblScope[@type='start-page']">
<xsl:value-of select="//teiHeader/fileDesc/sourceDesc/biblStruct/monogr/imprint/biblScope[@type='start-page']" />
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$DefValue" />
</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
</xsl:template>
to this:
<xsl:template name="GetStartPage">
<xsl:param name="DefValue"/>
<xsl:attribute name="initial-page-number">
<xsl:choose>
<xsl:when test="//teiHeader/fileDesc/sourceDesc/biblStruct/monogr/imprint/biblScope[@type='start-page'] and (string(number(//teiHeader/fileDesc/sourceDesc/biblStruct/monogr/imprint/biblScope[@type='start-page'])) != 'NaN')">
<xsl:value-of select="//teiHeader/fileDesc/sourceDesc/biblStruct/monogr/imprint/biblScope[@type='start-page']" />
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$DefValue" />
</xsl:otherwise>
</xsl:choose>
</xsl:attribute>
</xsl:template>
I also noticed a couple of typos in the markup of a review, which I fixed, and reported to LN so he can fix them in his copy.