KN and his team are about a third of the way through reworking the Japanese translations of spec items, and I've started the process of integrating the results back into the TEI repo. Going slowly so I can learn from what I'm reading, and check for misunderstandings.
Met with KT for our regular weekly trawl through the TODOs; evaluated changes to one article, accepted it and did the first copyedit; follow-ups with a couple of other submitters.
Met with JT and planned revisions to DSH paper requested by reviewer.
Editors' meeting with KT; did the consolidation of copyediting changes for LB's article, and sent the result to him; did the revision of my own article per reviewers; contacted some authors to remind them of requirement for images; and did a review of article 176. That was everything that was on my plate for the moment, I think.
Over the weekend, trawled through my tickets and did some work there; 6am to 7.10 this morning, had a Stylesheets Coop Group meeting online from home; at work, completed one of my tickets by creating a branch with a pull request, and debugged an issue with build log parsing on the TEI Jenkins server.
Separately with SA and GN, did the division of labour for the first stages in building our submission. I'll be creating the Quandary maze.
We've been discussing switching from woff fonts to SVG for site icons. Some of the problems we have with web fonts (woff etc.) are:
- Line height and rounding issues look slightly 'off' (spinner icon seems a bit wonky, vertical alignment is off by a pixel or two, etc.)
- Editing web fonts relies on external service and rebuilding each time we add an icon
- Using unicode addresses for all glyphs is impossible (*).
* To maximize design flexibility we have included multiple versions of, say, a map icon. We cannot give both of them the same unicode address. To overcome this we'd need multiple fonts.
Also, sometimes it's impossible to find a unicode address for the glyph you want to use - so you use a private use area address, or you abuse an orthography glyph because it looks similar to your icon/glyph - see hamburger menu.
So, to explore the implications of making this switch I built a test file that uses 4 methods of doing this, along with my recommendations.
Took the two halves written by GN and SA and moulded them into a whole, which I then committed to GitHub and sent to the panel folks. I'd like to get a couple of citations of the Librarians' work into the proposal, but still waiting for responses from them about URLs, and there may not be time.
Met with KT, pushed some decisions forward, and did half an evaluation of a resubmission (now waiting on author response to a question).
With SA and GN, outlined a submission and gathered some biblio refs.