The Nedj Nedj databases 2 The big picture 2.15 Mainly headings / 2.16 Mainly language info

2.15 MAINLY HEADINGS

In the narrow white band across the centre of Fig. 2.12 are to be found most of the column or field identifiers for the records below.

The band also contains:

● an automatically generated summary line for every record;

● determinative identifiers — up to three;

● transcription characters and respelling equivalents (captioned MacCht and EAWB)

● buttons taking you instantly to other screen layouts

● various ‘key’ fields

● common writings

● Gardiner number and category

These will be described in section 7.0 SUPPLEMENTARIES.

2.16 MAINLY LANGUAGE INFO

All that remains to be considered in Fig. 2.12 is the dark grey area above and to the right of the white ‘headings’ area. This contains five fields:

Fig. 2.161 The five fields in the ‘Mainly Language Info’ area

Meaning clue: green

The {meaning clue} field is where the summary line appears, transferred from the automatically generated summary line in the long blue field in the headings area. This is necessary because for a technical reason the automatic line does not include hieroglyph images until manually activated.

The summary line appears in the green {meaning clue} field when two necessary key combinations are struck: cmnd 2; cmnd 3.

cmnd 3 activates the summary line, converting it from:

Fig. 2.162a Summary line tAyi set, before cmnd 3 activation

to the following, by striking cmnd 3:

Fig. 2.162b Summary line tAyi set, after cmnd 3 activation

At the same time cmnd 3 inserts the glyphs into the {glyphline transfer cmnd 3} field:

Fig. 2.163a Vacant {glyphline transfer cmnd 3} field 

converting it to:

Fig. 2.163b {glyphline transfer cmnd 3} for tAyi set, after cmnd 3 activation

Alongside the blue {glyphline transfer cmnd 3} field is the grey {glyphline} field, which always has something in it, often apparently random hieroglyphs together with junk characters.

Fig. 2.164a {glyphline} field: automatic status for tAyi set record

But should you click in that field, they will at once change to something meaningful:

.

Fig. 2.164b {glyphline} field: status after clicking, for tAyi set record

This you will see is a match for what is at the top of the screen for this record:

Fig. 2.165 Glyph display for tAyi set record

By hitting cmnd 2, the expanded summary line is instantly carried into the blank {meaning clue} field:

Fig. 2.166a Blank {meaning clue} field: normal status

to make:

Fig. 2.166b {meaning clue} field for tAyi set record: after cmnd 3 / cmnd 2 activation

This is just an explanation of what is going on, which is to achieve a summary line with hieroglyphs. The hieroglyphs in the summary line are actually font characters, unlike those used in the glyphs area, which are pictures.

Fonts?

There are all sorts of fonts, not just alphabetic. Thus there are fonts for bullets, dingbats, animals, buildings ... and for hieroglyphs. And the only way to get hieroglyphs into the summary line in the Hierolex database is by using fonts, not the pictures in the glyph area of the Overview screen. A font normally has nearly 200 possibilities, or 47 for each of lower case and capitals (i.e. with or without using the shift key); and further 47s using option and shift option (on a Macintosh keyboard). As there are 1000 or more hieroglyphs, at least five fonts are required to cover this number. The fonts used here were obtained from <http://www.linguistsoftware.com/lhier.htm#Macintosh>; the same being available for PCs. (This URL operated successfully in 2013.) The names of the fonts used in the Nedj Nedj databases are: AnimalsLS, ArchitectureLS, EnvironmentLS, HieroglyphicsLS, MankindLS, and UtensilsLS.

This result is the same as the activated result in the blue {summary} field. So why go to all that trouble to do that? Largely so that the information can be made to occur in the occurrences and searcher panels, when desired.

The process has been slightly simplified, so that cmnd 5 does the action of both cmnd 3 and cmnd 2, as well as take you to the net record.

word for word JS (wd/wd): blue

The {word for word JS} field has become an all-purpose destination for dumping anything that appears of relevance to the meaning of the record being looked at; for example, it might contain summary lines of several similar records, for comparison. It originated with another purpose, but that is what it has become. And it is sufficiently useful to be worthy of retention.

comment transcription: yellow

Comments relating to the record’s transcription may be inserted in the {comment transcription} field. One such comment is:

Fig. 2.167 {comment transcription} field displaying a typical comment

<arm> INSTEAD OF <arm: TEEPEE> Gardiner writes: “D36 forearm ... Also in hieratic, less often in hieroglyphic, as a substitute for D37-44” [Gardiner:454:D36] <arm: teepee> is D37. SO THE RESPELLING SHOULD BE di

This relates to the entry:

Fig. 2.168 Glyph display for <arm> record

glyphline transfer cmnd 3: blue and glyphline: grey

The role of {glyphline transfer cmnd 3} and {glyphline} fields has been described above, under meaning clue.