|
Germanic Lexicon Project
Message Board
|
|
|
Author: Sean Crist (Nuance Communications)
Email: kurisuto1 at yahoo dot com
Date: 2007-07-09 13:31:20
Subject: Re: Volunteer wanted to check runes
> Most of my report seems to have been truncated by the message system.
> It was as below. This time I have removed a required backslash in front of
> "textara".
Sorry about that! I wish I had included a Preview button in the message board system.
> 16A0 f-rune textara{f} b0185 b0262 b0275x3
> 16A2 u-rune textara{u} b0185 b1142x3
> 16B3 c-rune textara{c} b0185 (BT has a more h-shaped figure than unicode table)
> 16B9 w-rune textara{w} b0185 b1285x6
> 16BE n-rune textara{n} b0185 b0705 b0717
> 16C1 i-rune textara{i} b0585 b0601x2
> 16C3 y-rune textara{y} [yr] b0185? BT has 3-legged symbol. Unicode 16C3 has two angles. I think 16A5 is the correct one.
> 16C8 p-rune textara{p} b0771? BT: "Runic &p-rune;", printed like P. Unicode has square C. Perhaps 16A6?
> 16D2 b-rune textara{b} b0064 b0085x2
> 16D6 e-rune textara{e} b0185
> 16D7 m-rune textara{m} b0652x2 b0669
> 16DA l-rune textara{l} b0185 b0603x2 b0615x4
> 16DD (not 16DC!) textara{backslash-ng} ng-rune b0592
> 16DE d-rune textara{d} b0192 b0193x2 b0652x3
> > Checked. In the table a page number without comment means all runes were ok. Problems noticed are *ed.
Thanks for checking this!!!
It looks like the * got lost. Sorry. :-/
So if I'm understanding: everything in the character database appears to be correct, except that there are issues with c-rune, y-rune, p-rune, and ng-rune, right?
> > * The first paragraph of b0669 (the continuation of MANN) is completely missing. It contains three runes.
This is a known problem.
Several hundred pages of B/T are imported from Bekie Marrett's project. Because Bekie and I had made some different choices, there are several issues involved in harmonizing her pages with the others. The missing piece of text you noticed has to do with this.
Often, an entry starts on one page and ends on another. Bekie and I handled these cases differently. She joined the broken entries right from the start. Of course, I intend for the the broken entries to be joined in the end, but I couldn't do this in the beginning, because the web-based correction system allows you to check out just one page at a time. So my plan was to join the broken entries after hand corrections are done.
So for right now, this difference in strategy means that there are mismatches where a range of Bekie's pages begins or ends. This is the case here. It's one of many things which remains to be fixed throughout the dictionary.
> > The third column is the allrunes LaTeX encoding for Anglo-Frisian runes. Could these please be added to the entity database?
So if I'm understanding, there's a font called "allrunes", and there's a file of macros which point to the characters, right?
Installing additional fonts on the system is not trivial, because it has to be handled by the sysadmin, and we want to avoid asking too much of her.
The project typesetting system actually uses TeX, not LaTeX, so I don't know whether the macros you mention would work. They might.
--Sean