Made a few bugfixes, and added title page info and some other placeholder content to the XML intro file for the book. Then added rendering for the title pages, and fixed the blank page issue. Also added some XSL messages to track rendering progress, and rationalized the build directory by deleted some old files with hard-coded orths (not needed now we're creating them on the fly). Did another proof of the LD & C article too.
Per the task in the previous post, draft documents are no longer displayed; instead, a boilerplate message is shown. A URL parameter allows editors or proofers to see the displayed document as normal.
Another site planning meeting today.
Sorted out navigational structure.
Revised our current outline according to today's discussed changes.
Sent revised outline to TI, SC (PAAS) for their review and comments
Some reviewer management; some work on the ODT conversion, which is now looking very nice (added page-numbering in the footer as well as some tweaks to make nested quote marks work properly); put the second article generated from XML into the copyediting chain; started work on the third, with some questions to the author, answered; and raised a question with SS about the last of the four articles.
New tasks arising:
On late duty, and trying to get difficult stuff finished while I still understood it.
Tasks for me from today's meeting:
A certain amount of one-step-forward-two-steps-back today. We've determined that there's no way with XEP to do small-caps, because the font does not have a small-caps variant, so I had to write some code to make small-caps programmatically with text analysis and styles. This caused horrible problems because it introduced lost of whitespace, due to the indenting between FO nodes. The only way to get rid of this was to set indent="no" on the XSL output, which leaves us with the need to manually insert spaces all over the place; that will take me a while, but ultimately it'll probably be the right thing to do. So the results are currently ugly as sin, but will eventually look a bit better.
Lots of other decisions as detailed in SMK's posts today.
If there are two instances of the same root's xml:id in a word's hyph, it's because the root morpheme is split up by an infix. These infixes need to be handled as follows:
-- when printing the hyph, replace the following strings:
-ʔ- with <ʔ>
+a+ with <a>
+C₂+ with <C₂>
+CVC+ with <CVC>
-- when generating the translated hyph,
a) Delete the second/rightmost instance of the root after these morphemes: inchoative (xml:id="ʔ"), characteristic (xml:id="CHAR"), out of control (xml:id="OC"):
For example: [[√ʔiɬ<CVC>n-úl • √eat<char>-attrib]]
BUT, if the root has no gloss, DO keep the second part of the root:
For example: [[k-√cúwˀ<CVC>x=ánaʔ • loc-√cúwˀ<char>x=ear]]
b) Delete the first/leftmost instance of the root before the repetitive morpheme (xml:id="REP"), and put the root symbol before the second part of the root.
For example: [[√p<a>tix̣ʷ • <rep>√test]]
Again, if the root has no gloss, keep the first part of the root.
For example: [[√p<a>tix̣ʷ • √p<rep>tix̣ʷ]]
|<< <||> >>|