Indicates uncertainty of degree=4 by flag | Indicates uncertainty of degree=3 by flag » Indicates uncertainty of degree=2 by flag « or brackets « », in this example the « » are not brackets but individual tokens Material is removed by a modern editor, marked by being within single braces Material is reconstructed by a modern editor, marked by being within square brackets Language, a is Aramaic, g is Greek, absent means Hebrew Material is corrected by an ancient editor, supralinear, marked by being within carets ^ ^ Material is corrected by an ancient editor, marked by being within double angle brackets > Material is corrected by a modern editor, marked by being within single angle brackets Indicates an alternative material, marked by being within brackets ( ) Whether there is a space after the last sign of a word and before the next word Representation of an addition between numerals Representation of a uncertain sign (degree 2) Representation of an uncertain sign (degree 1) The type of sign is stored in the feature type. Node type signīasic unit containing a single symbol, mostly a consonant, but it can also be Gives all lines where the feature biblical is absent. In queries, you can test for absence by means of #: For example, if the feature biblical is absent for node n, thenį.biblical.v(n) results in the Python value None, not the string 'None'. When we say that a feature is absent for a node, we mean that the node has no valueįor the feature. o the original transcription (as in the source files).e the ETCBC transliteration, or something that extends it.Some features come in three variants, a main variantĪnd two variants with the letter e of o after the feature name. We also supply the ETCBC transcription for Hebrew material. We have stripped all unicode orientation characters (202A-202E) The cause for encountering them in the opposite orientation might be that When we reproduce the orginal transcription, we put them all back into the left-to-right orientation, It turns out that in the files as we see them, they are consistently written as if in the right to left writingĭirection. There are bracketing constructs in the transcription, such as >, « ». We reduce them to single Hebrew unicodes per vowel. Probably in order to fine-tune the position of those points The vowels we encounter in those lexemes haveīeen transcribed by one or more special characters, The transcriptions are consonant only, the lexemes are pointed. We map the transcriptions and lexemes to Hebrew unicode. Text-Fabric supports up to three customizable section levels. Relations between nodes can be annotated with edge features. The type of every node is given by the featureĮvery node is linked to a subset of slots by On top of that, more complex textual objects can be represented as nodes.
#Dss transcription module red exclamation point series
The Text-Fabric model views the text as a series of atomic units, called
Originates from the biblical or non-biblical source file or both. The feature biblical below contains all the information to see whether the material Or contain a reconstruction (marked as reconstruction!) that is absent in the Here we have given precedence to the biblical versions, because they are either identical, There are a 14 lines that occur in both source files. In the source data files those scrolls are split between the files.ĭuring conversion, we have reunited the scrolls. Some scrolls contain biblical as well as non-biblical materials. In the biblical file, references to book, chapter and verse are marked In both files, the material is subdivided into scroll, fragment, line. The corpus consists of two files, one for the non-biblical scrolls and one for the TF docs for documentation on Text-Fabric.
In general, and the node types, features of the Here you find a description of the transcriptions of the Dead Sea Scrolls (DSS),
0 kommentar(er)
